Design Considerations for HTML Documents

Use Descriptive Titles

Bad

Newsletter

Spring Newsletter

Good

Medical Informatics Newsletter / Spring 1995

April 95 Informatics Newsletter

Remember

• Titles have many context independent uses, including bookmarks.

Be Consistent

• Place elements in the same location on related pages.
• Replace redundant information with a link to a single page.
• Avoid trite verbiage such as "more information can be found here."

Don't Micro Manage Your Page Layout

Try not to rely on:

• Font type and size
• Physical relationships between elements
• Browser-specific HTML extensions
• Graphics where plain text works just as well

Remember

• There are many different WWW browsers available.
• Each user has ultimate control over his/her display.

Don't Abuse HTML Tags

Even though HTML is flexible, if you bend it too far something will break. For example, the heading tags (<H1>, <H2>, etc.) are not just "big" text. They also specify document structure.

Remember

• HTML tags specify more than just text style.

Consider Text Only Browsers

Be Careful with Graphics

• Conserve vertical space whenever possible
• Use short horizontal or icon graphics for page titles
• Limit width of graphics to 450-500 pixels
• Use a thumbnail to jump to a larger image when appropriate
• Make images large enough, but no larger
• Provide alternate text when appropriate

Divide or Combine Pages as Appropriate

• Smaller "chunks" are easier browse
  • Provide inter-page links for multiple small pages
• Larger "chunks" are better for finding and printing
  • Provide intra-page links for large pages

Provide Context when Appropriate

• Home and parent page links
• Previous and next page links
• Link to original document (for copies)
• Reference, rather than quote, other documents

Use Relative URLs When Appropriate

Relative URL

images/picture.gif

Absolute URL

http://host.ufl.edu/images/picture.gif

Use "Sensible" File and Directory Names

• Use all lower case whenever possible
• Use short file and directory names whenever possible
• Use a "flat" directory hierarchy

Always Sign Your Work

• Identify the author or contact person
• Include a URL or email address
• Include a creation date or version number
• Include a copyright notice or disclaimer if appropriate

Remember Paper

• Make email addresses visible when appropriate
• Make URLs visible when appropriate
• Always make administrative information visible